Y Product Screen Factory · Control Room
DESIGN FREEZE: ACTIVE FILE CLASSIFICATION: COMPLETE INITIAL DUPLICATE CONSOLIDATION: COMPLETE WAVE 03 AUTHORITY RECONCILIATION: COMPLETE CRM · RESERVATIONS · ERP: READY FOR OWNER REVIEW WAVE 03 VISUAL QA: PASS NATIVE VISUAL PROOFS: VERIFIED PROOF INVENTORY: RECONCILED PROJECT-WIDE PHYSICAL VISUAL EVIDENCE: VERIFIED — 18 FAMILIES PAGE INVENTORY: RECONCILED — 197 RECORDS GAP REGISTER: 61 TOTAL · 58 CLOSED · 3 NON-DESIGN OPEN OPEN BACKLOG: 8 NON-CURRENT-DESIGN ITEMS OWNER REVIEW PDF: PENDING SAVE AND VERIFICATION PROJECT-WIDE VISUAL QA: PASS PROJECT-WIDE RESPONSIVE QA: PASS PROJECT-WIDE LANGUAGE QA: PASS ACCESSIBILITY DESIGN QA: PASS DESIGN BACKLOG: ZERO CURRENT-DESIGN ITEMS FINANCE · PLATFORM ADMIN · PORTALS · CATALOG · WEBSITE · CUSTOMER APP: READY FOR OWNER ACCEPTANCE PRODUCTION: NOT CLAIMED ASSISTIVE-TECH DEVICE VERIFICATION: PENDING DESIGN OWNER ACCEPTANCE: PENDING — MAY PROCEEDIMPLEMENTATION ALIGNMENT: BLOCKED UNTIL REPOSITORY EVIDENCE PASS
DESIGN FREEZE RECORD ACTIVE · 4 AUGUST 2026
DESIGN FREEZE:
ACTIVE
FREEZE DATE:
4 AUGUST 2026
FREEZE AUTHORITY:
YALLA THAILAND PRODUCT OWNER / CTO DESIGN CLOSEOUT
FROZEN SCOPE:
COMPLETE CURRENT AUTHORIZED YALLA THAILAND PRODUCT-DESIGN UNIVERSE
CLAUDE DESIGN:
COMPLETE FOR CURRENT AUTHORIZED SCOPE

The complete current authorized product-design scope is frozen.

No broad redesign, competing Home, competing App Shell, competing dashboard, replacement navigation, replacement information architecture or duplicate product family may be created without a new owner-authorized design mission.

ALLOWED AFTER FREEZE:
—verified visual-defect correction
—accessibility repair
—responsive repair
—Arabic, English or RTL/LTR repair
—implementation-alignment correction
—content maintenance
—evidence and delivery maintenance
—newly owner-authorized capability
—future capability activated by an approved contract or ADR
REQUIRES A NEW OWNER-AUTHORIZED DESIGN MISSION:
—replacement visual direction
—replacement navigation system
—replacement product architecture
—competing Home or App Shell
—competing CRM, ERP, Reservations, Finance or Admin shell
—rebuilding Voucher Desk
—rebuilding Catalog Administration
—rebuilding Yalla Bina
—rebuilding CRM pages 48–51
—rebuilding Reservations page 52
—rebuilding ERP page 53
—rebuilding pages 55–72
—hard deletion of retained historical sources
FINAL STATUS
CURRENT DESIGN BACKLOG:
ZERO
PROJECT-WIDE PHYSICAL VISUAL EVIDENCE:
VERIFIED — 18 FAMILIES
PROJECT-WIDE RESPONSIVE QA:
PASS
PROJECT-WIDE LANGUAGE QA:
PASS
ACCESSIBILITY DESIGN QA:
PASS
PROJECT-WIDE VISUAL QA:
PASS
DESIGN OWNER ACCEPTANCE:
PENDING — MAY PROCEED
ASSISTIVE-TECH DEVICE VERIFICATION:
PENDING — IMPLEMENTATION ALIGNMENT
IMPLEMENTATION ALIGNMENT:
PENDING REPOSITORY EVIDENCE PASS
PRODUCTION:
NOT CLAIMED

Yalla Thailand — canonical product design system

FULL CURRENT DESIGN SCOPE READY FOR OWNER ACCEPTANCE CURRENT AUTHORIZED DESIGN SCOPE COMPLETE NOT A DEPLOYED PRODUCT

This is a design factory of standalone Claude Design files — not a shipped product. Nothing here touches repositories, databases, deployment, DNS, secrets, production or Figma. Every page has now been classified once, in 45 Consolidation Matrix, and the systems are bounded in 44 Handoff Map. Counts below are recounted directly from the live file list. No screen here is source-of-truth for Booking Core, Finance or Payments; every screen is a design artifact pending visual acceptance.

Verified file count — physically recounted from the live file list, 4 August 2026, after wave 04–05
197
root design files — every .dc.html at the project root (162 at the start + 5 in wave 01 + 4 in wave 02 + 7 in wave 03 + 19 in waves 04–05)
193
active design artifacts — not all of them are pages: 184 screens / pages + 9 imported child components
184
screens / pages — the artifacts a reviewer opens as a screen or a document
9
imported child components (Voucher*) — imported by pages 35–37; not screens and not duplicates
4
archived files with an ARCHIVED__ prefix — content merged first. 7 pages created in wave 03; 0 hard deletions across all waves.
197 root design files = 193 active design artifacts + 4 archived files. 193 active design artifacts = 184 screens / pages + 9 imported child components. Machine-readable in canonical_file_inventory.csv — 197 rows, one per root design file — and canonical_screen_inventory.csv — 184 rows. Nineteen pages created in waves 04–05; zero deleted, zero archived.
01
Source Audit & Reconciliation
6 sources classified, conflicts resolved
02
Unified Design System
Tokens, type floor, elevation, chips, grid — patched this pass
03
Brand & WANAS Asset Guide
Logo integrated · WANAS transparency = PARTIAL, asset dependency
NEW · 29
Demo Data Registry
Single canonical customer/booking narrative — demo data only, not Booking Core or Finance truth
04–11
Staff Operating System
CRM → Reservations → ERP → Finance → Supplier → Partner → Admin → WANAS
12–22
Customer Application
Home → Guide → Bina/Nearby → Catalog → Transport/Hotels/Packages → Itinerary → My Trip → Booking → Muslim → WANAS → Account. 12A Onboarding: built in wave 02.
24–26
Flows, QA & Acceptance Gate
Wave 03 visual QA: PASS · project-wide visual QA: PASS across 18 families (73) · design owner-review gate: pending, may proceed · implementation alignment gate: blocked until the repository evidence pass
WAVES 04–05 · FULL DESIGN-UNIVERSE COMPLETION · 55–73 · 4 AUGUST 2026
Every remaining family completed, sixty-one gaps registered and fifty-eight closed
Twenty-eight families were audited from the live file list, not from a previous register. Six families had files but no front door — Finance, Platform Admin, Supplier, Partner, catalog customer experience and My Trip — and each now has a canonical entry point, role coverage, states and device evidence. Three gap-register rows remain — two implementation-verification rows and one outside-current-scope row — and none of them is design work. The separate open-backlog register holds eight non-current-design rows: two implementation verification, four future authorised, one outside current scope and one delivery-management item. Current design backlog: zero.
{{ p.n }}
{{ p.title }}
{{ p.body }}
Frozen families were again not redesigned: Voucher Desk, Catalog Administration, Yalla Bina, Ask Yalla, Website Home 42, App Shell 43, CRM 48–51, Reservations 52 and ERP 53. The passenger and schedule strips on 34 Passenger and Schedule Proof remain owner-accepted and untouched. Nothing was deleted; superseded 07, 08, 09, 10 and 16 files stay on disk as reference.
FINAL EVIDENCE & INVENTORY RECONCILIATION · 4 AUGUST 2026 · NO REDESIGN OF 55–72
Physical evidence now exists for all eighteen families, and the inventory matches the disk
This pass produced evidence and corrected metadata only. No page between 55 and 72 was redesigned and no competing Finance, Admin, Website, Portal, Catalog or Customer App screen was created.
Forty-four native proof files
True PNG, rendered at 1× with no downscale, in proofs/final-project-wide/native/. A principal screen, a responsive frame and an exception state for every materially completed family; one full-page proof for each preserved family. Every recorded pixel width equals the stated width — a file marked 1440 measures 1440, a file marked 390 measures 390.
Image format corrected
The six earlier review captures were JPEG bytes carrying a .png name. They are renamed to .jpg, moved to proofs/final-project-wide/thumbnails/ and labelled DOWNSCALED FIRST-FOLD REVIEW THUMBNAILS — never native proof. No file is named *.png.jpg.
page-inventory.json rebuilt
Rebuilt from physical reality, not patched: 197 page records including 55–73, current counts, missions 08 and 09, and the wave 03 figures kept only under an explicitly historical heading. Byte size, record count and a complete 64-character SHA-256 are recorded in export_checksums.txt.
Gap counts reconciled
61 gap rows registered, 58 closed, 3 remain and none is design work — two implementation-verification rows and one outside-current-scope row. The earlier “52 closed / 9 survive” headline is withdrawn. full_design_gap_register.csv.
Two registers kept separate
The gap register holds 61 rows. The open backlog register holds eight non-current-design rows: two implementation verification, four future authorised, one outside current scope, one delivery management. Current design backlog: zero.
Every export re-hashed
The eighteen-family QA manifest, the family completion matrix, the responsive, language and accessibility matrices and the proof inventory now cite physical files rather than declared frames. Fifty proof files and every machine-readable export carry byte size and a complete 64-character SHA-256.
The long-scroll Control Room PDF remains labelled CONTROL ROOM LONG-SCROLL REFERENCE and is not the Owner Review document. The seven-page wave 03 Owner Review was generated externally; its upload and Drive placement stay delivery-management actions and do not block the design closeout. Production is not claimed, and implementation alignment stays blocked until a repository evidence pass.
WAVE 03 · AUTHORITY RECONCILIATION & CORE PRODUCT COMPLETION · 48–54
CRM, Reservations and ERP completed — and every escalated decision resolved rather than re-asked
48
CRM Shell & Role Dashboards
One role-aware shell replaces seventeen unframed artefacts. Four dashboard variants, a sixteen-row navigation permission matrix, 1440 · 1280 · 834 · 390, and a permission-denied screen that is not a 404.
49
Pipeline & Lead Workspace
Both screens kept and completed — the ruling applied, not escalated. Kanban with an unassigned column, bulk assignment, thirteen lead states drawn, and the historical state model mapped rather than silently merged.
50
Customer 360 & Quote Builder
Identity spine with duplicate, merged and PDPA-erased states; Quote Builder as a first-class Sales capability with bilingual output and an approval threshold that blocks send. No net cost, no margin, no loyalty theatre.
51
Conversation Workspace & Evidence
Arabic RTL inside an English shell with four proved bidi cases, six inbox states, delivery failure with retry, 200 % text on the reply workflow, and WANAS bounded to drafting in the interface itself.
52
Reservations Lifecycle
One explicit state machine: twelve guarded transitions and six blocked shortcuts. Queue and detail, supplier evidence as evidence, amendment · cancellation · refund request, and ten named exceptions.
53
ERP & Operations
Four operational patterns replace the mobile card stack on a desktop canvas. Today board, pickup schedule, manifest, capacity-aware assignment, nine incident types, and a shift handover that cannot be accepted with unread items.
54
Lineage & Authority Register
The governance page: physical recount, the four escalations resolved, nine website pages classified with their unique value and destination, capability ownership, blueprint versus reality, and nineteen machine-readable exports.
Frozen families were not redesigned on this pass: Voucher Desk, Catalog Administration, catalog customer experience, Yalla Bina, Ask Yalla, the accepted Website Ecosystem Home and the accepted App Shell. Work on them was limited to navigation, status, lineage and stale-text correction. The passenger and schedule strips on 34 Passenger and Schedule Proof remain owner-accepted and untouched.
WAVE 03 CLOSEOUT CORRECTION · 4 AUGUST 2026 · NO REDESIGN OF 48–53
What this correction pass changed — counts, claim scope, recovered content, exports, proofs and the PDF
Count terminology corrected — historical wave 03 counts
Historical wave 03 state, superseded by the current 197 / 193 / 184 recount above. The 174 active artifacts are no longer called pages. 165 screens / pages plus 9 imported child components, stated the same way in 00, 25, 45, 54, both reports and every export.
Visual-QA claim scoped
A single global PASS overstated the evidence. Wave 03 (48–53) passes on rendered proof files; project-wide QA was scoped to PARTIAL on that pass. It is now PASS: forty-four native proof files physically evidence all eighteen families.
Section 23 recovery merged
The entry gate and the trust, support and emergency content now exist on 42 and 22. Only then were the section 23 pages reclassified — reference only, still on disk.
Exports reconciled
Historical wave 03 figures. canonical_file_inventory.csv stood at 178 rows — one per root design file — and canonical_screen_inventory.csv 165, one per screen / page. Both carry all fifteen required columns. Checksums recalculated.
Formal wave 03 proof files
30 rendered PNG proofs in proofs/wave03/, each with source page, viewport, language, zoom, timestamp, SHA-256 and a measured clipping result — proof inventory.
Owner-review document — source ready, PDF binary pending
The seven-page source is READY: page numbers, running headers, section breaks, readable body text at 100 % — Wave 03 Owner Review Document. The PDF binary exports/WAVE_03_OWNER_REVIEW_DOCUMENT.pdf is PENDING SAVE AND VERIFICATION; persistence is blocked by this environment, so it is not claimed as delivered. Steps in PDF_DELIVERY_LABELS.md. The earlier two-page ultra-tall file is kept only as CONTROL ROOM LONG-SCROLL REFERENCE. Delivery document, not a root screen, so the count stays 178.
OPEN REGISTER — ZERO CURRENT-DESIGN ITEMS. IMPLEMENTATION VERIFICATION, FUTURE-AUTHORIZED AND OUT-OF-SCOPE ROWS ONLY
{{ c }}
{{ b.item }}
{{ b.priority }}
{{ b.owner }}
{{ b.type }}
{{ b.blocks }}
{{ b.next }}
The six design rows that stood here on 4 August were closed in waves 04–05 — Finance depth, Platform Admin depth, portal depth, catalog depth, My Trip depth and website sizing. What remains is eight rows in total: two implementation-verification items, four future-authorised capabilities that need a contract or a separate authorisation, one out-of-scope programme item and one delivery task. Machine-readable in open_backlog_register.csv; full gap history in full_design_gap_register.csv and 73 Closeout.
WAVE 02 · CORE PRODUCT COMPLETION · 12A · 27 · 28 · 47
Four named gaps closed, and thirteen portal screens corrected at source
12A
Onboarding & First Run
Had zero files since the factory opened. Seven steps, six edge frames, 320 px, 200 % text, English mirror, all 25 required states accounted for. No authentication mechanism invented.
27 · 27A–27J
LINE Supplier Communication
Manual mode throughout — no API, no webhook, no auto-send, no live sync. Six-state vocabulary from drafted to Booking Core confirmed.
28
Cross-Channel Flow
Fourteen steps, three timelines, one booking. Thirteen named break modes, each detected and each owned. Only step 11 writes.
47
Portal Request Queue
Where a supplier's “yes” actually lands. Closes handoff gap 2 of 3; the other two are now classified, not open.
Also in wave 02: all thirteen Supplier and Partner screens corrected at source — “Confirm LOCK”, “Available — confirm”, “Mark boarded”, “Save changes”, quote creation, voucher sending and statement acceptance are now request-shaped, each screen carries the v1 read-only contract banner, and each links to 47. Rulings on 46.
WAVE 01 · 42–46 · CANONICALIZATION
The ecosystem is now visible from the front door, and every page has a ruling
42
Website Ecosystem Home
Canonical home. Five customer goals, every service exposed with an honest capability chip, 1440 · 834 · 390 plus an English mirror.
43
App Shell & Ecosystem Home
One five-tab shell replaces three. Three trip stages, the full More directory, 320 px, 200 % text and a location-denied state.
44
Cross-Product Handoff Map
Eight source-of-truth boundaries, twenty designed handoffs, six rules — and the three handoffs that had no destination screen — all three now resolved or formally classified.
45
Consolidation Matrix
All 178 root design files classified. The four previously escalated questions are resolved and applied. No owner-decision blocker remains.
46
Supplier & Partner Reconciliation
Thirteen Supplier and Partner source screens corrected against the read-only v1 contract. Direct-write controls were removed or converted into request-shaped actions routed to page 47. No unauthorized active control remains.
PRESERVED · 34 · 14 FILES · CURRENT CANONICAL PACKAGE
Yalla Voucher Desk — preserved, current canonical package
PRESERVED — CURRENT CANONICAL PACKAGE. No redesign is authorised and none was performed. The package covers the Central Voucher Desk, agent request and request workspace, supplier booking request and evidence review, the Booking Core confirmation gate, voucher preparation, the three audience variants, issue, per-recipient manual delivery, the manual LINE and WhatsApp handoff, and the Finance Register. Rasha is the primary Voucher Operator with a supported backup. One identity, one serial, one version chain; a customer and supplier operational voucher plus a restricted Internal Finance Voucher. Supplier messages stay evidence, Booking Core owns confirmation truth, and issue is locked until that confirmation exists. Manual delivery only — no LINE or WhatsApp integration is claimed. Any deferred Agent Self-Service scope is future and does not block preservation of this package.
PRIOR PASS · 31 · 10 FILES · 66 SCREENS
Yalla Bina complete product redesign — Direction A, Contextual Travel Companion
Full redesign of the Arabic-first traveller companion, grounded in yalla-thailand/yalla-nearby@main (Vite React SPA — 38 routes, 83 components, 48 services). 66 hi-fi screens at 390 px Arabic RTL plus English mirror, 320 px Android, iPhone safe areas and 200 % text. Seven-weight rhythm system replaces the same-weight card stack; one canonical Ask Yalla overlay; the Essential Apps directory built from scratch (no upstream implementation); weather and prayer promoted to real detail pages; nineteen hub destinations recovered; 18 system states drawn. Handoff: 43-component inventory, route map, tokens JSON, 9-phase migration plan, QA checklist, ZIP package.
PRIOR PASS · 30 · 9 FILES
Catalog Administration Control Center — catalog.yallathailand.net/dashboard
Redesign of the live catalog admin from the 13 current-state captures: catalog-only IA (11 destinations, CRM/ERP/finance modules removed), a routed product workspace replacing the six-tab modal, paired Arabic/English editing with a parity ledger, real destination · taxonomy · media · availability · review · quality surfaces, 25 desktop and 10 mobile screens, and an honest capability matrix with a 9-item backend gap register. Design-only: no repository change, no deploy.
Archived (not deleted — content merged first): the three "Recovered" duplicate files were reconciled into 04 CRM Lead and 05 Reservations Command Center in a prior pass. Wave 02 added a fourth: export-control-room.dc.html, a byte-level duplicate of this page left behind by an export, verified against it and archived as ARCHIVED__export-control-room.dc.html. It is the only file that left the active project. The nine unnumbered Voucher* files were checked and are not leftovers — pages 35, 36 and 37 import them. Full reasoning in 45.

Production matrix — by module, real file counts

{{ s.id }} {{ s.name }} {{ s.count }} {{ s.status }}

Status vocabulary: DESIGNED = drafted, not visually accepted · BUILT/SANDBOX = exists as a working Design Component · NOT BUILT = no file exists yet. Nothing here is ever labeled LIVE — this factory produces design artifacts, not shipped software.

Every active design — complete navigation index

All 193 active design artifacts — 184 screens / pages plus 9 imported child components — each reachable from here. This index exists so no active screen is an orphan: eight screens (04 CRM WhatsApp Arabic RTL, 05 Reservations Refund and Audit, 06 ERP Booking Queue and Pickup Schedule, 07 Finance Collections and Unpaid Bookings, 07 Finance Daily Close and Exception, 08 Supplier Requests and Availability, 11 WANAS Staff Search and Escalation, 26 Manager and Executive Exception Center) previously had zero incoming root-design links. The 4 ARCHIVED__ files are deliberately excluded and are not deleted.

00–03AFactory & foundations5
04CRM & customer engagement13
05Reservations6
06ERP / operations5
07Finance4
08Supplier portal6
09Partner portal6
10Platform admin7
11WANAS staff2
12–23Customer application & public website24
24–29Flows, QA, exception centre & demo data4
34Yalla Voucher Desk9 FILES · WAVE 0
30Catalog administration (catalog dashboard)9
31Yalla Bina product redesign (yalla-nearby)10
12A · 27 · 28 · 42–47Canonicalization, ecosystem & core completion9
32–33Location context, English mirrors & owner review7
34Voucher Desk — remaining screens & proofs5
35–37Tour voucher documents5
48–54Wave 03 — CRM, Reservations, ERP & authority register7
—Child components — imported, never orphans9

Frozen contract & standing decisions

Product contract
CATALOG-ITINERARY-MYTRIP-PRODUCT-CLOSEOUT-01 v1.0.1 governs Catalog → Product Detail → Compare → Itinerary → Quote → Booking → My Trip → Voucher → Live Trip → Memory → Return. Tiers: Economy / Standard / Premium / Luxury / VIP. Supplier identity, commission and wholesale cost never appear customer-side.
Language policy
Customer app: Arabic-first, RTL, English variants follow. WANAS adapts across Arabic dialects + English. Core staff CRM/ERP/Finance/Admin: English LTR (matches the strongest existing source). Partner Portal: Arabic RTL primary + English. Presentation family: Arabic-first, English only as product/technical terms.